Terminal services view toolbox

ABSTRACT

The disclosed architecture includes a view toolbox that offers a dynamic view of remote monitors and which enables the user to move quickly between one area and another across all remote monitors. The view toolbox enables the user to customize the view of the remote monitors ranging from fitting the view (remote desktop) of all remote monitors to the local computer display, showing a remote monitor at actual size on the local computer display, showing a dynamic view of each remote monitor, and/or allowing the user to move around the view area of the remote monitors.

BACKGROUND

Businesses are placing more demands on employees to travel. Even fornon-employment purposes, users seek to remotely access resources at workand at home. Advances in computing hardware and software enable users totravel with portable device such as laptop computers, for example, andthen connect to remote computing systems to access data.

However, in many cases the remote system has multiple monitors that whenaccessed remotely presents a view that is difficult to perceive. Oneexisting approach allows the user to work on multiple monitors connectedto a remote computer but does not provide a dynamic view of each monitoror a method to quickly navigate from one area to another. Anotherexisting approach allows remote connections; however, this approachminimizes to the actual size of the monitor in order to fit all monitorsto the screen, but there is no preview window or a direct way to get toa specific area of the remote computer by dragging the area in a previewwindow.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some novel embodiments described herein. This summaryis not an extensive overview, and it is not intended to identifykey/critical elements or to delineate the scope thereof. Its solepurpose is to present some concepts in a simplified form as a prelude tothe more detailed description that is presented later.

The disclosed architecture includes a view toolbox that offers a dynamicview of remote monitors and which enables the user to move quicklybetween one area and another across all remote monitors. The viewtoolbox enables the user to customize the view of the remote monitorsranging from fitting the view (remote desktop) of all the remotemonitors to the local computer display, showing a remote monitor atactual size on the local computer display, showing a dynamic view ofeach remote monitor, and/or allowing the user to move around the viewarea of the remote monitors.

To the accomplishment of the foregoing and related ends, certainillustrative aspects are described herein in connection with thefollowing description and the annexed drawings. These aspects areindicative of the various ways in which the principles disclosed hereincan be practiced and all aspects and equivalents thereof are intended tobe within the scope of the claimed subject matter. Other advantages andnovel features will become apparent from the following detaileddescription when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a view management system in accordance with thedisclosed architecture.

FIG. 2 illustrates a multi-monitor preview of a remote computer systemhaving three monitors over which a remote desktop extends.

FIG. 3 illustrates an embodiment of the preview window.

FIG. 4 illustrates a computer-implemented view management method inaccordance with the disclosed architecture.

FIG. 5 illustrates further aspects of the method of FIG. 4.

FIG. 6 illustrates a block diagram of a computing system that executes aterminal services toolbox in accordance with the disclosed architecture.

DETAILED DESCRIPTION

The disclosed architecture includes a view toolbox for interacting withapplications and data of a multi-monitor remote computer system. Thearchitecture provides a dynamic preview of remote computer desktop viathe view toolbox. The current viewable area on the local computerdisplay of a portion of the remote computer desktop is selected via aselection tool (e.g., a movable rectangle) that defines an area on ascaled-down preview of the remote computer system desktop across allmonitors.

The view toolbox enable a user to customize the view of remote monitorsbetween fitting all monitors to the local computer display and showingthe remote display at actual size. The view toolbox provides a dynamicview of each remote monitor, updated as the user opens and closes filesand performs other actions via the local computer. The view toolboxallows a user to move a rectangle the area of which defines a portion ofone or several remote monitors in a scaled-down preview of the remotecomputer monitors desktop. Moreover, the toolbox allows the user to jumpdirectly from one remote monitor to another remote monitor, for example.If the user can already see all of a remote display on the localcomputer display, the view toolbox is hidden and a message is presentedthat explains why the toolbox is not presented. Selecting (e.g., asingle click) a remote monitor preview, for example, in the scaled-downpreview automatically sets the local display viewing area to thespecific remote monitor.

Reference is now made to the drawings, wherein like reference numeralsare used to refer to like elements throughout. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding thereof. It maybe evident, however, that the novel embodiments can be practiced withoutthese specific details. In other instances, well known structures anddevices are shown in block diagram form in order to facilitate adescription thereof. The intention is to cover all modifications,equivalents, and alternatives falling within the spirit and scope of theclaimed subject matter.

FIG. 1 illustrates a view management system 100 in accordance with thedisclosed architecture. The system 100 includes a connection component102 of a local computer 104 that executes remote services 106 (e.g.,Windows Live Sync Remote Service by Microsoft Corporation) to establishcommunications between the local computer 104 and a remote computer 108having multiple monitors 110 connected thereto. The remote computer 108presents a remote desktop 112 as encompasses the remote display areas(114 and 116) of the monitors 110, and the local computer 104 has alocal display area 118 in a local monitor 120.

A preview component 122 of the local computer 104 presents a scaled-downpreview 124 of the remote desktop 112 in a preview window 126 in thelocal display area 118. The preview component 122 further presents apreview object 128 on the scaled-down preview 124 that defines an areaof the remote desktop 112 that is a current view as presented in thelocal display area 118.

In this example, the remote desktop 112 presents an object 130 that iseasily viewable when the user is sitting in front of the remote computer108 (e.g., when at home), but difficult to view remotely (e.g., while ontravel) when connecting via the remote services 106 to view the remotedesktop 112 and the object 130 (e.g., windows, webpages, documents,etc.) and associated object details (e.g., text, menu options, etc.).The user can now easily view the object 130 (or portions thereof) andassociated object details by moving the preview object 128 over theobject 130 (or portions thereof) in the preview 126.

In response, the preview component 122 (in cooperation with the remoteservices 106) dynamically presents an enlarged view 132 of the object130 (or portion thereof) and object details circumscribed by the previewobject 128 in the scaled-down preview 124, in the local display area118.

In operation, the remote computer 108 extends series of drawing commandsto the local computer 104. The local computer 104 assembles the commandsand presents a copy of the remote display areas (114 and 116) onto thelocal display area 118 (also, the local desktop). The scaled-downpreview window 124 is a copy of the remote desktop 112 that isassembled.

The preview object 128 enables of the zoom (enlargement) changes and thepreview object 128 movement is performed on the local computer 104. Inother words, the local computer 104 has information about all of thescreens of the remote desktop 112 that may be currently displayed. Thelocal computer 104 receives all the information needed to compute acomplete rendering of the remote desktop 112 and the objects, screens,etc., displayed via the remote desktop 112. The bi-directionalcommunications between the local computer 104 and the remote computer108 is such that the any change on the remote computer 108 is quicklyeffected on the local display area 118 for data that is in the currentview (e.g., for partial object 132) and in the scaled-down preview 124for user selection and preview.

The preview component 122 (and remote services 106) interfaces tooperating system programs and modules such that in a multi-monitorsituation implementation on the remote computer 108 the orientationinformation of the monitors 110 is obtained as well as monitorresolution and other settings of the remote monitors 110.

As part of the remote services protocol the remote computer 108 sendsthis information upon connection by the local computer 104. Moreover,each time the remote desktop 112 changes resolution or monitorconfiguration the remote computer sends the change information to thelocal computer 104.

Put another way, the preview component enables dynamic viewing of theremote desktop in the local display area in response to movement of thepreview object relative to the scaled-down preview. The scaled-downpreview includes a control object that zooms in on the area defined bythe preview object and enlarges the corresponding view presented in thelocal display area. The scaled-down preview includes a control objectthat zooms out of the area defined by the preview object and reduces thecorresponding view presented in the local display area. The previewobject is dragged over the scaled-down preview of the remote desktop andthe preview component dynamically changes the current view in the localdisplay area to a new view as defined according to a new area of thepreview object.

The preview component automatically changes the current view to adisplay area of one of the monitors in response to selection of anobject (where objects include actionable graphics in preview component126 such as a monitor object (the preview object 128), a Min object, Maxobject, slider objects, etc.) in the scaled-down preview. The previewcomponent automatically sets the local display area to an entire remotedisplay area of a remote monitor in response to selection of an object(e.g., a remote monitor object) in the scaled-down preview of the remotedesktop. The preview object is a rectangle through which the area in thescaled-down preview of the remote desktop is viewed. The previewcomponent automatically updates the scaled-down preview of the remotedesktop in response to interaction with applications and data of theremote computer via the current view on the local display area.

FIG. 2 illustrates a multi-monitor preview 200 of a remote computersystem having three monitors over which a remote desktop extends. Here,the remote computer uses three monitors (not shown), as represented bythe three sections in the scaled-down preview 124. The remote desktop112 extends across the remote display areas of the three monitors asindicated by three windows one (1), two (2) and three (3). When the usermoves (drags) the preview object 128 over the third window, the displayarea 118 of the local monitor 120 dynamically enlarges and presents theportion 202 of the third window within the preview object 128. The usercan then comfortably view and interact with objects such as controls 204and images and/or other data 206 in the portion 202. Similarly, when theuser moves (drags) the preview object 128 over the first window, thedisplay area 118 of the local monitor 120 dynamically changes andpresents the portion 208 of the first window within the preview object128. The user can then comfortably view and interact with objects suchas text in the portion 208.

FIG. 3 illustrates an embodiment of the preview window 126. The previewwindow 126 can include a slider control object 300 that enables the userto zoom in or zoom out of the portion of the third window over which thepreview object 128 is dragged. In other words, as the user moves theslider toward the Max position, the corresponding portion in the localdisplay area 118 is enlarged to provide the zoom-in effect, and as theuser moves the slider toward the Min position the corresponding portionin the local display area 118 is reduced to provide the zoom-out effect.Moving the slider entirely to the left (the lowest Min setting) willshow the entire remote desktop 112 in the local display area 118.

The Max and Min objects can be made actionable. For example, whenselecting the Min control object, the preview component 126automatically sets the local display area 118 to present all remotemonitors. In an alternative embodiment, the same result can be made tooccur when the user clicks the outer edge of the preview area. Whenselecting the Max control object, the preview component can be made toautomatically set the local display area 118 to show a ratio (e.g.,1-to-1) of pixels on the remote monitor(s). Other actions can beutilized as desired.

The preview component and preview window provide the dynamic view andthe ability to change the local view of the remote computer to fit oneor all remote monitors as well as dynamic interaction with the user. Inother words, a dynamic preview of the remote computer is provided. Inone implementation, the current viewable area showing is defined by arectangle preview object that defines the space for the local displayarea. Additionally, moving a pointing device such as a mouse over thepreview window 128 changes the pointer to a hand so that the user candrag the preview window 128 in order to move from the current view to adifferent area or monitor for a new view. Selecting on a monitor preview(e.g., third window) automatically sets the local viewing area to thespecific monitor selected.

In an alternative implementation, rather than providing the previewwindow as an always-on or always-off feature, the user can hover thepointer over a part of the remote desktop as presented in the localdisplay area, and the preview window will automatically appear for apredetermined period of time (e.g., three seconds) and then disappear.In another implementation, hovering the pointer over a toolbox area(e.g., menu item or button) will automatically present the previewwindow, and then moving away from the toolbox area or buttons will causethe preview window to disappear.

Included herein is a set of flow charts representative of exemplarymethodologies for performing novel aspects of the disclosedarchitecture. While, for purposes of simplicity of explanation, the oneor more methodologies shown herein, for example, in the form of a flowchart or flow diagram, are shown and described as a series of acts, itis to be understood and appreciated that the methodologies are notlimited by the order of acts, as some acts may, in accordance therewith,occur in a different order and/or concurrently with other acts from thatshown and described herein. For example, those skilled in the art willunderstand and appreciate that a methodology could alternatively berepresented as a series of interrelated states or events, such as in astate diagram. Moreover, not all acts illustrated in a methodology maybe required for a novel implementation.

FIG. 4 illustrates a computer-implemented view management method inaccordance with the disclosed architecture. At 400, communications isestablished between a local computer and a remote computer that enablesaccess of applications and data on the remote computer via the localcomputer. The remote computer has multiple monitors via which a remotedesktop is presented. At 402, commands and images associated with theremote desktop of the remote computer are received at the localcomputer. At 404, a scaled-down preview of the remote desktop ispresented on a local computer display. At 406, an area of thescaled-down preview is selected. At 408, a current view of the selectedarea is presented on the local computer display for user interaction.

FIG. 5 illustrates further aspects of the method of FIG. 4. Each of theblocks represents a single step that can be added to the methodrepresented by the flow chart of FIG. 4. At 500, the current view isdynamically changed to a new view that corresponds to a new areaselected on the scaled-down preview. At 502, the size of the currentview in the local computer display is adjusted via an adjustment controlassociated with the scaled-down preview. At 504, the current view isdynamically changed to a new view of a portion of the remote desktop inresponse to dragging a preview object over the scaled-down preview. At506, the scaled-down preview of the remote desktop is updated inresponse to interaction with the applications and data of the remotecomputer via the current view on the local computer display. At 508, anotification is presented that explains hiding of the scaled-downpreview when a remote monitor is fully presented in the local computerdisplay.

As used in this application, the terms “component” and “system” areintended to refer to a computer-related entity, either hardware, acombination of software and tangible hardware, software, or software inexecution. For example, a component can be, but is not limited to,tangible components such as a processor, chip memory, mass storagedevices (e.g., optical drives, solid state drives, and/or magneticstorage media drives), and computers, and software components such as aprocess running on a processor, an object, an executable, a module, athread of execution, and/or a program. By way of illustration, both anapplication running on a server and the server can be a component. Oneor more components can reside within a process and/or thread ofexecution, and a component can be localized on one computer and/ordistributed between two or more computers. The word “exemplary” may beused herein to mean serving as an example, instance, or illustration.Any aspect or design described herein as “exemplary” is not necessarilyto be construed as preferred or advantageous over other aspects ordesigns.

Referring now to FIG. 6, there is illustrated a block diagram of acomputing system 600 that executes a terminal services toolbox inaccordance with the disclosed architecture. In order to provideadditional context for various aspects thereof, FIG. 6 and the followingdescription are intended to provide a brief, general description of thesuitable computing system 600 in which the various aspects can beimplemented. While the description above is in the general context ofcomputer-executable instructions that can run on one or more computers,those skilled in the art will recognize that a novel embodiment also canbe implemented in combination with other program modules and/or as acombination of hardware and software.

The computing system 600 for implementing various aspects includes thecomputer 602 having processing unit(s) 604, a computer-readable storagesuch as a system memory 606, and a system bus 608. The processingunit(s) 604 can be any of various commercially available processors suchas single-processor, multi-processor, single-core units and multi-coreunits. Moreover, those skilled in the art will appreciate that the novelmethods can be practiced with other computer system configurations,including minicomputers, mainframe computers, as well as personalcomputers (e.g., desktop, laptop, etc.), hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

The system memory 606 can include computer-readable storage (physicalstorage media) such as a volatile (VOL) memory 610 (e.g., random accessmemory (RAM)) and non-volatile memory (NON-VOL) 612 (e.g., ROM, EPROM,EEPROM, etc.). A basic input/output system (BIOS) can be stored in thenon-volatile memory 612, and includes the basic routines that facilitatethe communication of data and signals between components within thecomputer 602, such as during startup. The volatile memory 610 can alsoinclude a high-speed RAM such as static RAM for caching data.

The system bus 608 provides an interface for system componentsincluding, but not limited to, the system memory 606 to the processingunit(s) 604. The system bus 608 can be any of several types of busstructure that can further interconnect to a memory bus (with or withouta memory controller), and a peripheral bus (e.g., PCI, PCIe, AGP, LPC,etc.), using any of a variety of commercially available busarchitectures.

The computer 602 further includes machine readable storage subsystem(s)614 and storage interface(s) 616 for interfacing the storagesubsystem(s) 614 to the system bus 608 and other desired computercomponents. The storage subsystem(s) 614 (physical storage media) caninclude one or more of a hard disk drive (HDD), a magnetic floppy diskdrive (FDD), and/or optical disk storage drive (e.g., a CD-ROM drive DVDdrive), for example. The storage interface(s) 616 can include interfacetechnologies such as EIDE, ATA, SATA, and IEEE 1394, for example.

One or more programs and data can be stored in the memory subsystem 606,a machine readable and removable memory subsystem 618 (e.g., flash driveform factor technology), and/or the storage subsystem(s) 614 (e.g.,optical, magnetic, solid state), including an operating system 620, oneor more application programs 622, other program modules 624, and programdata 626.

The one or more application programs 622, other program modules 624, andprogram data 626 can include the entities and components of the system100 of FIG. 1, the entities and components of the system 200 of FIG. 2,the view and components of FIG. 3, and the methods represented by theflowcharts of FIGS. 4-5, for example.

Generally, programs include routines, methods, data structures, othersoftware components, etc., that perform particular tasks or implementparticular abstract data types. All or portions of the operating system620, applications 622, modules 624, and/or data 626 can also be cachedin memory such as the volatile memory 610, for example. It is to beappreciated that the disclosed architecture can be implemented withvarious commercially available operating systems or combinations ofoperating systems (e.g., as virtual machines).

The storage subsystem(s) 614 and memory subsystems (606 and 618) serveas computer readable media for volatile and non-volatile storage ofdata, data structures, computer-executable instructions, and so forth.Such instructions, when executed by a computer or other machine, cancause the computer or other machine to perform one or more acts of amethod. The instructions to perform the acts can be stored on onemedium, or could be stored across multiple media, so that theinstructions appear collectively on the one or more computer-readablestorage media, regardless of whether all of the instructions are on thesame media.

Computer readable media can be any available media that can be accessedby the computer 602 and includes volatile and non-volatile internaland/or external media that is removable or non-removable. For thecomputer 602, the media accommodate the storage of data in any suitabledigital format. It should be appreciated by those skilled in the artthat other types of computer readable media can be employed such as zipdrives, magnetic tape, flash memory cards, flash drives, cartridges, andthe like, for storing computer executable instructions for performingthe novel methods of the disclosed architecture.

A user can interact with the computer 602, programs, and data usingexternal user input devices 628 such as a keyboard and a mouse. Otherexternal user input devices 628 can include a microphone, an IR(infrared) remote control, a joystick, a game pad, camera recognitionsystems, a stylus pen, touch screen, gesture systems (e.g., eyemovement, head movement, etc.), and/or the like. The user can interactwith the computer 602, programs, and data using onboard user inputdevices 630 such a touchpad, microphone, keyboard, etc., where thecomputer 602 is a portable computer, for example. These and other inputdevices are connected to the processing unit(s) 604 through input/output(I/O) device interface(s) 632 via the system bus 608, but can beconnected by other interfaces such as a parallel port, IEEE 1394 serialport, a game port, a USB port, an IR interface, etc. The I/O deviceinterface(s) 632 also facilitate the use of output peripherals 634 suchas printers, audio devices, camera devices, and so on, such as a soundcard and/or onboard audio processing capability.

One or more graphics interface(s) 636 (also commonly referred to as agraphics processing unit (GPU)) provide graphics and video signalsbetween the computer 602 and external display(s) 638 (e.g., LCD, plasma)and/or onboard displays 640 (e.g., for portable computer). The graphicsinterface(s) 636 can also be manufactured as part of the computer systemboard.

The computer 602 can operate in a networked environment (e.g., IP-based)using logical connections via a wired/wireless communications subsystem642 to one or more networks and/or other computers. The other computerscan include workstations, servers, routers, personal computers,microprocessor-based entertainment appliances, peer devices or othercommon network nodes, and typically include many or all of the elementsdescribed relative to the computer 602. The logical connections caninclude wired/wireless connectivity to a local area network (LAN), awide area network (WAN), hotspot, and so on. LAN and WAN networkingenvironments are commonplace in offices and companies and facilitateenterprise-wide computer networks, such as intranets, all of which mayconnect to a global communications network such as the Internet.

When used in a networking environment the computer 602 connects to thenetwork via a wired/wireless communication subsystem 642 (e.g., anetwork interface adapter, onboard transceiver subsystem, etc.) tocommunicate with wired/wireless networks, wired/wireless printers,wired/wireless input devices 644, and so on. The computer 602 caninclude a modem or other means for establishing communications over thenetwork. In a networked environment, programs and data relative to thecomputer 602 can be stored in the remote memory/storage device, as isassociated with a distributed system. It will be appreciated that thenetwork connections shown are exemplary and other means of establishinga communications link between the computers can be used.

The computer 602 is operable to communicate with wired/wireless devicesor entities using the radio technologies such as the IEEE 802.xx familyof standards, such as wireless devices operatively disposed in wirelesscommunication (e.g., IEEE 802.11 over-the-air modulation techniques)with, for example, a printer, scanner, desktop and/or portable computer,personal digital assistant (PDA), communications satellite, any piece ofequipment or location associated with a wirelessly detectable tag (e.g.,a kiosk, news stand, restroom), and telephone. This includes at leastWi-Fi (or Wireless Fidelity) for hotspots, WiMax, and Bluetooth™wireless technologies. Thus, the communications can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices. Wi-Fi networks use radiotechnologies called IEEE 802.11x (a, b, g, etc.) to provide secure,reliable, fast wireless connectivity. A Wi-Fi network can be used toconnect computers to each other, to the Internet, and to wire networks(which use IEEE 802.3-related media and functions).

The illustrated and described aspects can be practiced in distributedcomputing environments where certain tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed computing environment, program modules can be located inlocal and/or remote storage and/or memory system.

What has been described above includes examples of the disclosedarchitecture. It is, of course, not possible to describe everyconceivable combination of components and/or methodologies, but one ofordinary skill in the art may recognize that many further combinationsand permutations are possible. Accordingly, the novel architecture isintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.Furthermore, to the extent that the term “includes” is used in eitherthe detailed description or the claims, such term is intended to beinclusive in a manner similar to the term “comprising” as “comprising”is interpreted when employed as a transitional word in a claim.

1. A computer-implemented view management system having computerreadable media that store executable instructions executed by aprocessor, comprising: a connection component of a local computer thatexecutes remote services to establish communications between the localcomputer and a remote computer having multiple monitors connectedthereto, the remote computer presenting a remote desktop across themonitors and the local computer having a local display area; and apreview component of the local computer that presents a scaled-downpreview of the remote desktop in the local display area, the previewcomponent further presents a preview object on the scaled-down previewthat defines an area of the remote desktop that is a current view aspresented in the local display area.
 2. The system of claim 1, whereinthe preview component enables dynamic viewing of the remote desktop inthe local display area in response to movement of the preview objectrelative to the scaled-down preview.
 3. The system of claim 1, whereinthe scaled-down preview includes a control object that when selectedzooms in on the area defined by the preview object and enlarges thecorresponding view presented in the local display area.
 4. The system ofclaim 1, wherein the scaled-down preview includes a control object thatwhen selected zooms out of the area defined by the preview object andreduces the corresponding view presented in the local display area. 5.The system of claim 1, wherein the preview object is dragged over thescaled-down preview of the remote desktop and the preview componentdynamically changes the current view in the local display area to a newview as defined according to a new area of the preview object.
 6. Thesystem of claim 1, wherein the preview component automatically changesthe current view to a display area of one of the monitors in response toselection of the one of the monitors in the scaled-down preview.
 7. Thesystem of claim 1, wherein the preview component automatically sets thelocal display area to an entire remote display area of a remote monitorin response to selection of the remote monitor in the scaled-downpreview of the remote desktop.
 8. The system of claim 1, wherein thepreview object is a rectangle through which the area in the scaled-downpreview of the remote desktop is viewed.
 9. The system of claim 1,wherein the preview component automatically updates the scaled-downpreview of the remote desktop in response to interaction withapplications and data of the remote computer via the current view on thelocal display area.
 10. A computer-implemented view management systemhaving computer readable media that store executable instructionsexecuted by a processor, comprising: a connection component of a localcomputer that executes remote services to establish communicationsbetween the local computer and a remote computer having multiplemonitors connected thereto, the remote computer presenting a remotedesktop across the monitors and the local computer having a localdisplay area; and a preview component of the local computer thatpresents a scaled-down preview of the remote desktop in the localdisplay area, the preview component further presents a preview object onthe scaled-down preview that defines an area of the remote desktop thatis a current view as presented in the local display area, the previewcomponent enables dynamic viewing of the remote desktop in the localdisplay area in response to movement of the preview object relative tothe scaled-down preview.
 11. The system of claim 10, wherein thescaled-down preview includes a control object that zooms in on the areadefined by the preview object and enlarges the corresponding viewpresented in the local display area, and zooms out of the area definedby the preview object and reduces the corresponding view presented inthe local display area.
 12. The system of claim 10, wherein the previewobject is dragged over the scaled-down preview of the remote desktop andthe preview component dynamically changes the current view in the localdisplay area to a new view as defined according to a new area of thepreview object.
 13. The system of claim 10, wherein the previewcomponent automatically changes the current view to a display area ofone of the monitors in response to selection of an object in thescaled-down preview.
 14. The system of claim 10, wherein the previewcomponent automatically sets the local display area to an entire remotedisplay area of a remote monitor in response to selection of an objectin the scaled-down preview of the remote desktop.
 15. Acomputer-implemented view management method executed via a processor,comprising: establishing communications between a local computer and aremote computer that enables access of applications and data on theremote computer via the local computer, the remote computer havingmultiple monitors via which a remote desktop is presented; receiving atthe local computer commands and images associated with the remotedesktop of the remote computer; presenting a scaled-down preview of theremote desktop on a local computer display; selecting an area of thescaled-down preview; and presenting a current view of the selected areaon the local computer display for user interaction.
 16. The method ofclaim 15, further comprising dynamically changing the current view to anew view that corresponds to a new area selected on the scaled-downpreview.
 17. The method of claim 15, further comprising adjusting sizeof the current view in the local computer display via an adjustmentcontrol associated with the scaled-down preview.
 18. The method of claim15, further comprising dynamically changing the current view to a newview of a portion of the remote desktop in response to dragging apreview object over the scaled-down preview.
 19. The method of claim 15,further comprising updating the scaled-down preview of the remotedesktop in response to interaction with the applications and data of theremote computer via the current view on the local computer display. 20.The method of claim 15, further comprising presenting a notificationthat explains hiding of the scaled-down preview when a remote monitor isfully presented in the local computer display.